* document spelling fixes.
and deciphering of the arc filter project option interpolation.
* improve line break insertion in build table.
* reword some option documentation.
* whitespace
<section xml:id="Qt">
<title>Building with Qt Creator</title>
<para>
-Qt provides a lovely IDE (Integrated Development Evironment) with an
+Qt provides a lovely IDE (Integrated Development Environment) with an
editor and debugger. Its use is strongly encouraged for those new to C++.
Once you have Qt correctly installed, just opening the <filename>
CMakeLists.txt</filename> from
</para>
<variablelist>
<varlistentry>
- <term>GPSBABEL_WITH_LIBUSB=no|pkgconfig|system*|included*|custom</term>
+ <term>GPSBABEL_WITH_LIBUSB = no|pkgconfig|system*|included*|custom</term>
<listitem>
<para>note that libusb is NOT used on windows.</para>
<variablelist>
</listitem>
</varlistentry>
<varlistentry>
- <term>GPSBABEL_WITH_SHAPELIB=no|pkgconfig|included*|custom</term>
+ <term>GPSBABEL_WITH_SHAPELIB = no|pkgconfig|included*|custom</term>
<listitem>
<variablelist>
<varlistentry>
</listitem>
</varlistentry>
<varlistentry>
- <term>GPSBABEL_WITH_ZLIB=no|pkgconfig|included*|custom</term>
+ <term>GPSBABEL_WITH_ZLIB = no|pkgconfig|included*|custom</term>
<listitem>
<variablelist>
<varlistentry>
GPSBabel style file.
</para>
<para>For a format to be described by a style file, it must be predictable and
-generally readable by humant. Formats with binary or unreadable content
+generally readable by a human. Formats with binary or unreadable content
are not good fits for this scheme. It should have:
<simplelist>
<member>A fixed header at the beginning, if it has any at all. This is called a 'prologue'.</member>
consists of three pieces of information: the FIELD TYPE, a DEFAULT VALUE, and
a PRINTF CONVERSION (for output). In many cases, not all pieces are used,
but all 3 pieces are required. Additionally, an fourth field is supported
-that modifies the behaviour of the field being described.
+that modifies the behavior of the field being described.
</para>
<para>FIELDS should be defined in the style file in the logical order that they
appear in the data, from left to right. This is the order in which they are
intersections. That means that, while navigating that route using a
GPS unit, the course pointer would aim to the inside of that curve or
intersection, and only when you have passed that point will the GPS
-aim to the next waypoint in the route. This behaviour is useful in
+aim to the next waypoint in the route. This behavior is useful in
marine navigation but when biking, for instance, it may be a bit late
to decide where to turn to in an intersection.</para>
is used.
</para>
<para>
-With <option>rte</option> and <option>trk</option> optinos, if
-is possible, altitude, creation_time and microsecond fields of waypoints
-are updated by interpolation.
+With either the <option>rte</option> or <option>trk</option> option
+the altitude and creation_time of the projected waypoints
+are updated, if possible, by interpolation from the route or track data.
</para>
<para>
This is most useful if you are trying to obtain the closest points in
<para>
This option splits tracks at segment boundaries into multiple tracks. This
-is useful to restore the behaviour of GPSBabel versions up to 1.3.6 which
+is useful to restore the behavior of GPSBabel versions up to 1.3.6 which
didn't support track segment markers and automatically put each segment into
a separate track.
</para>
<para>
GPSBabel creates route points during the transformation process named "RPTnnn" where nnn is a numeric part.</para>
<para>
-Using this option GPSBabel can be configured to replace the "RPT" part of the generated names by the name of the source track during the transformation process. This is especially usefull if several differently named tracks are contained in the source file which should each be transformed into routes.
+Using this option GPSBabel can be configured to replace the "RPT" part of the generated names by the name of the source track during the transformation process. This is especially useful if several differently named tracks are contained in the source file which should each be transformed into routes.
</para>
<example xml:id="transform_rptname">
<title>Convert a GPX track to a GPX route, deleting the original track, naming the generated points like the original track name.</title>
<para>
This filter removes points based on their proximity to each other.
-For waypoints a point is removed if it is within the specified distance of a preceeding point.
+For waypoints a point is removed if it is within the specified distance of a preceding point.
For routes and tracks consecutive points are removed until the distance between the bracketing points is greater than the specified distance.
</para>
<para>
- Much like the <option>erase</option> this optio erases the data in the GPS.
+ Much like the <option>erase</option> this option erases the data in the GPS.
It does not transfer data before doing so, making it much faster. This may
be handy in a work flow where you want to transfer the data from the GPS,
check it on a map, and then remove it from the unit.
<para>
- Much like the <option>erase</option> this optio erases the data in the GPS.
+ Much like the <option>erase</option> this option erases the data in the GPS.
It does not transfer data before doing so, making it much faster. This may
be handy in a work flow where you want to transfer the data from the GPS,
check it on a map, and then remove it from the unit.
<para>
Uses the given value instead of the value from the tag OffsetTime, OffsetTimeOriginal or OffsetTimeDigitized.
This is useful when the image doesn't contain an OffsetTime* tag and the offset is different from the local time, or when the image contains a tag that is incorrect.
- The format of this option should match that of the tag OffsetTime*, specifcally it must be "+HH:MM" or "-HH:MM".
+ The format of this option should match that of the tag OffsetTime*, specifically it must be "+HH:MM" or "-HH:MM".
</para>
<para>
If the camera was using China Standard Time, e.g. in the winter in Taiwan, then you should supply
</para>
<para>
-At the end of the transfer, baud rate is switched to back to the default
-of 9600. If connection breaks, the unit stucks at high baud rate, a power
-cycle reverts to original state.
+At the end of the transfer the baud rate is switched to back to the default
+of 9600. If the connection breaks and the unit is stuck at a high baud rate power
+cycling should restore the original baud rate.
</para>
<para>
<para>
- For a large list of points (or whyever) it can be useful when
- no bitmaps are displayed on device. With this option no bitmap
- is stored and displayed.
+ For a large list of points it may be desirable if
+ no bitmaps are displayed on the device. With this option no bitmaps
+ are stored and displayed.
</para>
<para>
<userinput>
<para>
Garmin points of interest files may contain data in two languages.
-If you attempt to read a dual language Garmin points of interest file without specifiying which language
+If you attempt to read a dual language Garmin points of interest file without specifying which language
to use GPSBabel will print an error message containing the language codes used in the file.
Subsequently you may use one of these codes with the languagecode
option to specify which language to use.
The dump-file option is primarily for debugging is module. It lets you
provide a file which contains the raw stream of bytes coming from the
device. This is useful for capturing device state to describe to a
-developer that can't actually access hte physical device as well as mocking
+developer that can't actually access the physical device as well as mocking
the entire device for automated regression testing.
</para>
<para>
</table>
<para>
-The default behaviour when gps-week-rollover isn't given (or is a negative number)
+The default behavior when gps-week-rollover isn't given (or is a negative number)
is to assume the input data has been logged within the preceding 1024 weeks from the
time gpsbabel is run, which should be perfectly fine in almost all cases.
</para>
</tbody>
</tgroup>
</table>
-<para>Windows users of GPSBabel version 1.5.2 or less may have to explicitly specifiy a bit rate of 115200 or lower.</para>
+<para>Windows users of GPSBabel version 1.5.2 or less may have to explicitly specify a bit rate of 115200 or lower.</para>
<example xml:id="skytraq-on-linux">
<title>Command showing skytraq download of tracks and erasing the logger on Linux</title>
projects / gpsbabel.git / commitdiff